Closed
Conversation
added 13 commits
June 9, 2025 19:13
added 9 commits
June 12, 2025 09:50
cheeyanglee
reviewed
Jun 17, 2025
3 tasks
added 3 commits
June 17, 2025 13:03
This reverts commit 1ba1a74.
Author
|
Closing as it was based on 3.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created
k3s-standard.jsonpackage added toedge-image.jsonandedge-image-dev.jsonThe only addOn required as of today is network-policy that
allow ingress to kube-system NS only for DNS, metrics and kube-api access and deny rest
Merge Checklist
All boxes should be checked before merging the PR
Description
Any Newly Introduced Dependencies
How Has This Been Tested?
Launched bulit image and verified location of manifest
In separate vm launched k3s and put manifests in given location.
Network-policies were picked by k3s few seconds later